Native Selling Platform

ABSTRACT

Example embodiments of the present disclosure include a system comprising a computer-readable storage medium storing at least one program and a computer-implemented method for providing a native selling platform. In example embodiments, an operating system of a device is configured to share information with other devices and services using native functionalities of the operating system. An indication to share an image of an item is received. A sharing user interface is presented that includes a plurality of services with which the image of the item is sharable. A selection of a publication system from the plurality of services is received. In response, a listing user interface is presented that includes fields for input of parameters used to generate a listing for the item in the image. Parameters and an indication to list the item are received and are shared with the publication system to cause the publication system to create the listing for the item.

CLAIM OF PRIORITY

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/587,721, filed Dec. 31, 2014, entitled “NativeSelling Platform,” the entire disclosure of which is incorporated byreference herein in its entirety.

FIELD

The present disclosure relates generally to data processing and, in aspecific example embodiment, to providing a native selling platform.

BACKGROUND

Typically, when a user wants to access an application on a mobiledevice, the user must unlock the device, navigate from a home page tofind the application, and launch the application. The user also,typically, cannot receive data from the application when the mobiledevice is in a standby mode.

BRIEF DESCRIPTION OF DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating an example embodiment of anetwork architecture of a system used to provide a native sellingplatform.

FIG. 2 is a block diagram illustrating an example embodiment of a mobiledevice.

FIG. 3 is a block diagram illustrating some components of the operatingsystem used in providing the native selling platform.

FIG. 4 is a block diagram illustrating an example embodiment of thepublication system.

FIGS. 5A-5K are example user interfaces presented on a mobile devicethat illustrates use of the native selling platform.

FIG. 6 is a flow diagram of an example method for creating a listingusing the native selling platform.

FIG. 7 is a flow diagram of an example method for replying to a questionusing the native selling platform.

FIG. 8 is a flow diagram of an example method for managing post-sale ofan item using the native selling platform.

FIG. 9 is a simplified block diagram of a machine in an example form ofa computing system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the present invention. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques have not been shown in detail.

Example embodiments described herein provide systems and methods forproviding a native selling platform on a mobile device of the user. Thenative selling platform is integrated into an operating system on themobile device and utilizes the functionalities of the operating systemto facilitate exchange of data and provisioning of notifications withoutthe user having to activate and run a separate application.

In example embodiments, an operating system of a mobile device isconfigured to share information with other devices and services usingnative functionalities of the operating system. An indication to sharean image of an item is received. A sharing user interface is presentedthat includes a plurality of services with which the image of the itemis sharable. A selection of a publication system from the plurality ofservices is received. In response, a listing user interface is presentedthat includes fields for input of parameters used to generate a listingfor the item in the image. Parameters and an indication to list the itemare received and are shared with the publication system to cause thepublication system to create the listing for the item.

As a result, one or more of the methodologies described hereinfacilitate data exchange and presentation of notifications. The userdoes not need to unlock the mobile device to navigate to an applicationthat the user wants to activate. Additionally, the user does not need toactivate any applications in order to exchange information or obtainnotifications. When these effects are considered in aggregate, one ormore of the methodologies described herein may obviate a need forcertain efforts or resources that otherwise would be involved innavigating the mobile device and accessing notifications. Computingresources used by one or more machines, databases, or devices (e.g.,within the network environment) may be reduced. Examples of suchcomputing resources include processor cycles, network traffic, memoryusage, data storage capacity, power consumption, and cooling capacity.

With reference to FIG. 1, an example embodiment of a high-levelclient-server-based network environment 100 that provides an environmentin which a native selling application on a mobile device may beimplemented is shown. A networked system 102, in an example form of anetwork-server-side functionality, is coupled via a communicationnetwork 104 (e.g., the Internet, wireless network, cellular network, ora Wide Area Network (WAN)) to one or more mobile devices 110 and 112.FIG. 1 illustrates, for example, a web client 106 operating via abrowser (e.g., such as the Internet Explorer® browser developed byMicrosoft® Corporation of Redmond, Wash. State), and a programmaticclient 108 executing on respective mobile devices 110, 112.

The mobile devices 110, 112 may each comprise a smartphone, tablet,laptop, or any other communication device that a user may utilize toaccess the networked system 102. In some embodiments, each mobile device(e.g., mobile device 110) may comprise a display module (not shown) todisplay information (e.g., in the form of user interfaces). In furtherembodiments, the mobile device 110 may comprise one or more of a touchscreen, accelerometer, camera, microphone, and Global Positioning System(GPS) device. The mobile devices 110, 112 may be a device of a user,which is used to trigger processing of information, post information,and receive notifications from the networked system 102.

In one embodiment, the networked system 102 includes or is linked to anetwork-based marketplace that manages digital goods, publishespublications comprising item listings of items available on thenetwork-based marketplace, and manages payments for these marketplacetransactions. The mobile device (e.g., mobile device 110) may interfacewith the networked system 102 via a connection with the network 104.Depending on the form of the mobile device 110, any of a variety oftypes of connections and networks 104 may be used. For example, theconnection may be Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or anothertype of cellular connection. Such a connection may implement any of avariety of types of data transfer technology, such as Single CarrierRadio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, or other data transfertechnology (e.g., fourth generation wireless, 4G networks). When suchtechnology is employed, the network 104 may include a cellular networkthat has a plurality of cell sites of overlapping geographic coverage,interconnected by cellular telephone exchanges. These cellular telephoneexchanges may be coupled to a network backbone (e.g., the publicswitched telephone network (PSTN), a packet-switched data network, orother types of networks).

In another example, the connection to the network 104 may be a WirelessFidelity (Wi-Fi, IEEE 802.11x type) connection, a WorldwideInteroperability for Microwave Access (WiMAX) connection, or anothertype of wireless data connection. In such an embodiment, the network 104may include one or more wireless access points coupled to a local areanetwork (LAN), a wide area network (WAN), the Internet, or anotherpacket-switched data network. In yet another example, the connection tothe network 104 may be a wired connection (e.g., an Ethernet link), andthe network 104 may be a LAN, a WAN, the Internet, or anotherpacket-switched data network. Accordingly, a variety of differentconfigurations are expressly contemplated.

In various embodiments, the data exchanged within the networkenvironment 100 may be dependent upon user-selected functions availablethrough one or more client or user interfaces (UIs). The UIs may beassociated with a client device, such as the mobile device 110 executingthe web client 106 (e.g., an Internet browser), which may be incommunication with the networked system 102. The UIs may also beassociated with one or more applications executing on the mobile device110, such as a mobile application or operating system designed forinteracting with the networked system 102 or with a social networkplatform hosted by a third party server 128.

Turning specifically to the networked system 102, an API server 114 anda web server 116 are coupled to, and provide programmatic and webinterfaces respectively to, an application server 118. The applicationserver 118 hosts a publication system 120, which comprises one or moremodules, applications, or engines, and which can be embodied ashardware, software, firmware, or any combination thereof. Theapplication server 118 is, in turn, coupled to one or more databaseservers 122 facilitating access to one or more information storagerepositories or databases 124. In one embodiment, the database 124 is astorage device that stores content (e.g., product listings, storeinformation, advertisements, user accounts) that is used by thepublication system 120.

In example embodiments, the publication system 120 publishes content ona network (e.g., Internet). As such, the publication system 120 providesa number of publication functions and services to users that access thenetworked system 102. For example, the publication system 120 can host amarketplace application that provides a number of marketplace functionsand services to users, such as publishing, listing, and price-settingmechanisms whereby a seller may list (or publish information concerning)goods or services (also collectively referred to as “items”) for sale, abuyer can express interest in or indicate a desire to purchase suchgoods or services, and a price can be set for a transaction pertainingto the goods or services. However, it is noted that the publicationsystem 120 may, in alternative embodiments, be associated with anon-marketplace environment such as an informational (e.g., searchengine) or social networking environment. The publication system 120will be discussed in more detail in connection with FIG. 4.

FIG. 1 also illustrates a third party application 126 executing on thethird party server 128 that can exchange information with theapplication server 118 or with the mobile devices 110 and 112. The thirdparty application 126 may have programmatic access to the networkedsystem 102 via a programmatic interface provided by the API server 114.The third party application 126 is associated with any organization thatconducts transactions with, or provides services to, the applicationserver 118 or to users of the mobile devices 110 and 112. For example,the third party application 126 can be associated with a network basedsocial network platform (e.g., Instagram®, Facebook®, Twitter®,Google+®, Pinterest®, LinkedIn®, or the like) that provides a platformfor members to build and maintain social networks and relations amongmembers and that allows members to post information and accessadditional information via, for example, links.

While the publication system 120 is shown in FIG. 1 to form part of thenetworked system 102, it will be appreciated that, in alternativeembodiments, the publication system 120 may form part of a separateservice that is distinct from the networked system 102. Additionally,while the example network environment 100 of FIG. 1 employs aclient-server architecture, a skilled artisan will recognize that thepresent disclosure is not limited to such an architecture.

Referring now to FIG. 2, a block diagram illustrating an exampleembodiment of a mobile device 200 is shown. The mobile device 200 can bean implementation of the mobile device 110 or 112. In some embodiments,the mobile device 200, in communication with the networked system 102,performs the methodologies described herein. The mobile device 200includes a processor 202. The processor 202 can be any of a variety ofdifferent types of commercially available processors suitable for mobiledevices 200 (e.g., an XScale architecture microprocessor, aMicroprocessor without Interlocked Pipeline Stages (MIPS) architectureprocessor, or another type of processor). A memory 204, such as a randomaccess memory (RAM), a Flash memory, or other type of memory, istypically accessible to the processor 202. The memory 204 can be adaptedto store an operating system (OS) 206, as well as application programs208. The processor 202 is coupled, either directly or via appropriateintermediary hardware, to a display 210 and to one or more input/output(I/O) devices 212, such as a keypad, a touch panel sensor, a microphone,and the like. Similarly, in some example embodiments, the processor 202is coupled to a transceiver 214 that interfaces with an antenna 216. Thetransceiver 214 can be configured to both transmit and receive cellularnetwork signals, wireless data signals, or other types of signals viathe antenna 216, depending on the nature of the mobile device 200.Further, in some configurations, a GPS receiver 218 can also make use ofthe antenna 216 to receive GPS signals.

In example embodiments, the OS 206 is specially configured to provide orcomprise a native selling platform. The functionalities of the nativeselling platform are based on basic functionalities of the speciallyconfigured OS 206 (e.g., iOS). In conventional systems, an applicationuses an operating system memory to run and perform functions and thenpasses information via a network to other systems or applications. Incontrast, example embodiments comprise a system whereby basic functionsfor selling are embedded directly into the native operating system(e.g., IOS or Android). As such, the operating system can formulate andpass information that would normally be performed from within a runningapplication without the need of the application.

Referring now to FIG. 3, some components of the OS 206 that are used inproviding the native selling platform are shown. The components includea device management component 302, a networking component 304, a userinterface component 306, an application component 308, a share component310, and a selling component 312. Not all components of the OS 206 havebeen included in FIG. 3. In general, components, protocols, structures,and techniques (e.g., memory management component, security component)not directly related to functions of exemplary embodiments are not shownor discussed in detail.

The device management component 302 communicates with a device driverwhich acts as an interface for communicating with devices of the mobiledevice 200. Accordingly, the device management component 302 can causethe device drivers to provide commands or receive data from the coupleddevices. The coupled devices include, for example, any I/O devices 212of the mobile device 200 (e.g., a touch screen sensor, a keypad), thedisplay 210, and the GPS receiver 218. As such, the device managementcomponent 302 allows for receipt of data used to create listings on thenetworked system 102.

The networking component 304 manages communications over the network104. As such, the networking component 304 allows the mobile device 200to connect via the network 104 to the application server 118, thepublication system 120, and the third party server 128 in order toexchange data. Data transmitted to the publication system 120 caninclude, for example, listing information and images used to createlistings on the publication system 120, replies to questions, andpost-sale information (e.g., where to pick up an item). Data receivedfrom the publication system 120 can include questions from potentialbuyers and notifications that an item has sold.

The user interface component 306 manages user interfaces on the mobiledevice 200. The user interfaces may include a home page of the mobiledevice 200 through which the user may unlock the mobile device 200 inorder to access various functions of the mobile device 200. In exampleembodiments, the home page is configurable to include notifications fromthe publication system 120. Additionally, the user interface may includea sharing interface (e.g., AirDrop).

The application component 308, which in some embodiments is a part of akernel, provides an interface between applications 208 and the hardware.The OS 206 comprises a set of services which simplify development andexecution of various application programs. Executing an applicationprogram involves creation of a process by the application component 308(e.g., kernel), which assigns memory space and other resources,establishes a priority for the process in multi-tasking systems, loadsprogram binary code into memory, and initiates execution of theapplication program which then interacts with the user and with thedevices.

The share component 310 provides a service that enables the user totransfer files without using email or a mass storage device. In oneexample, the share component 310 corresponds to a specially-configuredversion of AirDrop for iOS and OS X devices. When the share component310 is activated, the OS 206 attempts to share files, for example,through the cloud, with other devices that are also configured to sharefiles and exchange data. In one embodiment, the share component 310passes the information to a nearby system via short range wireless andthe nearby system then transmits the files to the publication system120.

The selling component 312 manages basic functions for selling via the OS206 of the mobile device. In example embodiments, the selling componentprovides forms or data to create user interfaces through which the userinteracts to list items for sale on the publication system 120.Additionally, the selling component 312 assists in providingnotifications related to items listed on the publication system 120 andan ability to respond to the notifications.

Referring now to FIG. 4, an example block diagram illustrating multiplecomponents that, in one embodiment, are provided within the publicationsystem 120 of the networked system 102 is shown. In this embodiment, thepublication system 120 comprises a network-based marketplace where items(e.g., goods or services) may be offered for sale. The items maycomprise digital goods (e.g., currency, license rights) as well asphysical goods. The publication system 120 may be hosted on dedicated orshared server machines (not shown) that are communicatively coupled toenable communications between the server machines. The multiplecomponents themselves are communicatively coupled (e.g., via appropriateinterfaces), either directly or indirectly, to each other and to variousdata sources, to allow information to be passed between the componentsor to allow the components to share and access common data. Furthermore,the components may access the one or more databases 124 via the one ormore database servers 122.

The publication system 120 provides a number of publishing, listing, andprice-setting mechanisms whereby a seller (e.g., individual, store,company) may list (or publish information concerning) goods or servicesfor sale, a buyer can express interest in or indicate a desire topurchase such goods or services, and a price can be set for atransaction pertaining to the goods or services. To this end, thepublication system 120 may comprise at least one publication engine 402and one or more auction engines 404 that support auction-formatlistings, fixed-price listings, and price setting mechanisms (e.g.,English, Dutch, Chinese, Double, Reverse auctions).

A store engine 406 allows a seller to group listings within a “virtual”store, which may be branded and otherwise personalized by and for theseller. Such a virtual store may also offer promotions, incentives, andfeatures that are specific and personalized to the seller. In oneexample, the seller can offer a plurality of items as Buy-It-Now itemsin the virtual store, offer a plurality of items for sale or auction, ora combination of both.

In order to make content available via the networked system 102 asvisually informing and attractive as possible, the publication system120 includes an imaging engine 408 that enables users to upload imagesor videos for inclusion within publications and to incorporate images orvideos within viewed publications. The imaging engine 408 can alsoreceive image data from a user as a search query and utilize the imagedata (e.g., metadata) to identify an item depicted or described by theimage data. In accordance with example embodiments, the imaging engine4085 can use images or other digital content obtained from third partymedia hosting sites.

A content creation engine 410 allows users (e.g., sellers) toconveniently author publications, content, or listings of items. In oneembodiment, the content may pertain to goods or services that a user(e.g., a seller) wishes to transact via the publication system 120. Inother embodiments, a user can create content that is an advertisement orother form of publication (e.g., tutorial video).

A content management engine 412 allows the users to manage suchpublications, listings, or content. Specifically, where a particularuser has authored or published a large number of content, the managementof such content may present a challenge. The content management engine412 provides a number of features (e.g., auto-relisting, inventory levelmonitors) to assist the user in managing such content.

A post-sale management engine 414 assists users with a number ofactivities that typically occur post-sale. For example, upon completionof an auction or sale facilitated by the one or more auction engines404, the item needs to be delivered to the buyer. Accordingly, thepost-sale management engine 414 assists in printing shipping labels,estimating shipping costs, and suggesting shipping carriers.Additionally, the post-sale management engine 414 can facilitatein-person pick-up of the item.

A messaging engine 416 is responsible for the generation and delivery ofnotifications to users of the networked system 102. Such notificationsinclude, for example, advising users regarding the status of listingsand best offers (e.g., providing an acceptance notice to a buyer whomade a best offer to a seller) and providing questions from potentialbuyers. The messaging engine 416 utilizes any one of a number of messagedelivery networks and platforms to deliver messages to users. Forexample, the messaging engine 416 can deliver electronic mail (e-mail),an instant message (IM), a Short Message Service (SMS), text, facsimile,or voice (e.g., Voice over IP (VoIP)) messages via wired networks (e.g.,the Internet), a Plain Old Telephone Service (POTS) network, or wirelessnetworks (e.g., mobile, cellular, WiFi, WiMAX).

Although the various components of the publication system 120 have beendefined in terms of a variety of individual modules and engines, askilled artisan will recognize that many of the items can be combined ororganized in other ways and that not all modules or engines need to bepresent or implemented in accordance with example embodiments.Furthermore, not all components of the publication system 120 have beenincluded in FIG. 4. In general, components, protocols, structures, andtechniques not directly related to functions of exemplary embodiments(e.g., pricing engine, dispute resolution engine, loyalty promotionengine, personalization engines) have not been shown or discussed indetail. The description given herein simply provides a variety ofexemplary embodiments to aid the reader in an understanding of thesystems and methods used herein.

FIGS. 5A-5K are example user interfaces that illustrate the use of thenative selling platform (e.g., via the user interface component 306) onthe mobile device 200. FIG. 5A show a user interface 500 of an imagecapture application displayed on the mobile device 200. In oneembodiment, the image capture application is caused to be activated bythe application component 308. As shown, the user of the mobile device200 is attempting to capture an image of an item (e.g., sunglasses) thatthe user is interested in selling via the publication system 120. Theuser captures the image by selecting a button 502 on the mobile device200.

Once the image is captured, an icon 504 displaying the captured image ispresented by the image capture application as shown in FIG. 5B.Additionally, the captured image can be displayed in the user interface500. The captured image can be edited or photo corrected using the imagecapture application.

In example embodiments, the share component 310 of the operating system206 is activated to access the native selling platform. In oneembodiment, the user selects the captured image (e.g., selecting theicon 504) and indicates a desire to share the captured image. Forexample, the captured image may be shared by selecting a share icon 506as shown in FIG. 5C.

Once the captured image is selected to be shared, a sharing userinterface 508 is presented as shown in FIG. 5D (via the share component310 in connection with the user interface component 306). In the exampleshown in FIG. 5D, the captured image is shown with a check icon 510 toindicate that the captured image is selected to be shared. The sharinguser interface 508 presents a plurality of services and contacts thatthe captured image can be shared with. These services include, forexample messages 512, e-mail 514, the cloud 516, and the publicationsystem 518 (e.g., illustrates as “ebay”).

In the present example, the user selects the publication system 518 toinitiate a native selling process. In response, the selling component312 (in connection with the user interface component 306) causes a userinterface depicting a form 520 to be presented to the user as shown inFIG. 5E. In some cases, the data for generating the form 520 is obtainedfrom the publication system 120 (via the share component 310). In otherembodiments, data for generating the form 520 is locally stored andaccessed by the mobile device 200 or provided by the selling component312. The form 520 can include an area 522 where the captured image isdisplayed along with a description area 524. Additionally, the user can,for example, set a price, provide a condition for the item depicted inthe captured image, and indicate shipping costs. As previouslyindicated, the user can also take advantage of the native platform ofthe OS 206 for photo correction of the captured image in the area 522.

The form 520 can be scrolled up to display more information.Accordingly, as shown in FIG. 5F, the form 520 is scrolled to showoptions for posting information to various social networks. For example,the user can select to post a listing (or information regarding thelisting) generated based on the form 510 to Instagram or Twitter. Theuser makes the selection by using a toggle 526 and 528. As a result, theuser can generate and post a listing to the publication system 120(e.g., eBay) while simultaneously posting either the same listing or alink to the listing to one or more social networks. When posting to asocial network, such as Instagram, hashtags that go with the listing areprovided. Examples of the hashtags 530 are shown at a bottom of the form520. The hashtags 530 can be automatically provided (e.g., for generalhashtags) or derived from data entered in the form 520 (e.g., for itemspecific hashtags). The user also has an option 532 to manually add morehashtags.

Once the user is satisfied with content in the form, the user selects alist indicator or button (e.g., shown at a top of the form 520 in FIG.5E) to cause a listing to be generated by the publication system 120. Inresponse to the selection of the list indicator, the data in the form520 is shared by the share component 310 with the publication system 120(e.g., via the network component 304). In particularly, the contentcreation engine 410 of the publication system 120 receives the data andgenerates content in the example form of a listing that is posted to thepublication system 120. Simultaneously, data is shared with the selectedsocial networks that results in listing information or links to thelisting at the publication system 120 to be posted on the socialnetwork.

Referring now to FIG. 5G, a home page 534 of the mobile device 200 isshown. Because the item was listed natively by use of the OS 206 (e.g.,the selling component 312 and sharing component 310), nativenotifications of the selling platform are able to take advantage of thefunctionalities of the OS 206. As a result, the display of anynotification does not involve any applications running on the mobiledevice 200. As such, a notification 536 in the form of a question from apotential buyer is displayed on the home page 534 while the mobiledevice is in a standby mode (e.g., locked mode). In this example, thepotential buyer in inquiring as to whether the item comes with a case.The notification may be shared by the publication system 120 (e.g., themessaging engine 416) with the mobile device 200 via the share component310 of the OS 206 and caused to be displayed by the share component 310(or selling component 312) in connection with the user interfacecomponent 306.

In response to receiving the notification 536, the user can swipe orslide on the notification 536 in order to reply. In example embodiments,the user does not need to unlock the mobile device 200 in order toreply. Referring now to FIG. 5H, the home page 534 is shown after theswipe. The user can mark the notification 536 as being read or reply tothe notification 536 (e.g., right in line on the notification 534). Asindicated, the mobile device 200 is still in a standby or locked mode.

The selection of the reply indicator 528 (and while the mobile device200 is still in standby or locked mode) causes a reply user interface540 to be presented (e.g., by the user interface component 306) to theuser as shown in FIG. 5I. The reply user interface 540 provides a replybox 542 where the user enters the reply and a “send” indicator 544 tosend the reply. In example embodiments, the reply is “shared” by theshare component 310 (e.g., via the network component 304) with thepublication system 120 (e.g., with the messaging engine 416).Subsequently, the publication system 120 (e.g., by way of the messagingengine 416) provides the reply to the potential buyer. As previouslydiscussed, because the notification and the subsequent reply takeadvantage of the native functionalities of the OS 206, no applicationsneed to be activated and, in some embodiments, the phone remains instandby or locked mode.

A further notification 546 in the form of a sold notification from thepublication system 120 is displayed on the home page 534 in FIG. 5J. Inthis example, the sold notification indicates that the item that theuser listed using the native selling platform has sold. Similar to thenotification 536 involving the question, the notification 546 is sharedby the publication system 120 (e.g., the messaging engine 416) with themobile device 200 via the share component 310 of the OS 206. As such,the notification 546 is not based on any application running on themobile device 200, but received, for example, from the cloud or network104 while the mobile device is in a standby mode.

In response to receiving the notification 546, the user can swipe orslide on the notification 546 in order to interact with the notification546. In example embodiments, the user does not need to unlock the mobiledevice 200 in order to interact. Referring now to FIG. 5K, the home page534 is shown after the swipe. The user can select to print a label toship the item that is sold or set up pick-up for the item. Alternativeembodiments may comprise other post-sale options. If the user chooses toprint the label, a selection of a print label indicator 548 causesdisplay of a shipping label. Alternatively, a selection of a “pick-upnow” indicator 550 causes display of a user interface that allows theuser to indicate a location and time for pick-up of the item. In exampleembodiments, the pick-up information is “shared” by the share component310 with the publication system 120 (e.g., with the messaging engine416). Subsequently, the publication system 120 (e.g., by way of themessaging engine 416) provides the pick-up information to the buyer. Asindicated, the mobile device 200 is still in a standby or locked mode.In one embodiment, the selection of the “pick-up now” indicator 548 caninitiate a process that uses a shuttle service to arrange forgeo-located item delivery.

FIG. 6 is a flow diagram of an example method 600 for creating a listingusing the native selling platform provided by the OS of a mobile device.Operations of the method 600 are discussed as being performed by (orthrough the use of) the OS 206 on the mobile device 200. In operations602, an indication to share a selected image of an item is received. Theimage may have been captured by an image capture application on themobile device 200. The image is displayed on the mobile device 200, anda share icon selected in connection with the selected image. The sharecomponent 310 receives the indication of the selection of the image andthe share icon.

In response to the selection of the share icon, a sharing user interfaceis provided on the mobile device by the share component 310 (e.g., inconnection with the user interface component 306) in operation 604. Thesharing user interface shows the selected image and provides a list ofcontacts or services (e.g., in the form of selectable icons) that theuser can select from with which to share the selected image. In exampleembodiments, the list of contacts includes the publication system 120.

In operation 606, a selection to share the selected image with thepublication system 120 is received. Accordingly, the share component 310receives a selection of an icon from the sharing user interface thatcorresponds with the publication system 120.

The receipt of the selection to share the image with the publicationsystem 120 causes presentation of a listings user interface to beprovided in operation 608. The listing user interface is provided by theselling component 312 (e.g., in connection with the user interfacecomponent 306) and comprises a plurality of fields in which the user canprovide parameters for listing an item depicted in the select image forsale. The parameters include, for example, a price, condition, shippingcost, and a description. The listing user interface also shows one ormore social networks to which a post related to the listing for the itemfor sale may be posted. The social networks include, for example,Instagram and Twitter. The user can select to post to one or more ofthese social networks (e.g., by toggling on a selection). Additionally,hashtags for the social networks that correspond to the listing areshown and the user can manually add more hashtags.

In operation 610, the parameters and indications to post to one or moresocial networks is received by the share component 310 and used toupdate the sharing user interface displayed on the mobile device 200.Once the user is satisfied for the parameters and selection of socialnetworks, the user can select a list indicator.

A list indication based on the selection of the list indicator isreceived in operation 612. In response to the receiving of the listindication, the parameters are shared with the publication system 120 bythe share component 310 (e.g., via the network component 304). Thepublication system 120 receives the parameters, and the content creationengine 410 generates content in the example form of a listing for thesale of the item depicted in the selected image using the parameters.The listing is posted to the publication system 120 in operation 614.Simultaneously, data can be shared with the indicated social networksthat results in listing information or links to the listing at thepublication system 120 to be posted on the selected social networks. Thesharing of the listing information or the links can be performed by theshare component 310 or by the publication system 120 (e.g., after thecreation of the listing).

FIG. 7 is a flow diagram of an example method 700 for replying to aquestion using the native selling platform. Because the item was listednatively by use of the OS 206, native notifications of the sellingplatform are able to take advantage of the functionalities of the OS206. In operation 702, a question from a potential buyer is detected atthe publication system 120.

In example embodiments, the question can be shared by the publicationsystem 120 (e.g., via the messaging engine 416) with the mobile device200 via the share component 310 of the OS 206. A notificationcorresponding to the question is then presented in operation 704. Inexample embodiments, the notification is displayed on the home page ofthe mobile device 200 while the mobile device 200 is in standby orlocked mode.

In operation 706, an indication to reply is received by the OS 206. Inone embodiment, the user selects a reply indicator associated with thenotification in order to reply. The mobile device 102 detects theselection and in response provides a reply box in which the user of themobile device 200 provides the reply in operation 708. Alternatively,the user can select to mark the notification as being read by selectinga “mark as read” indicator. In example embodiments, the user does notneed to unlock the mobile device 200 (or exit the standby mode) in orderto reply.

The user provides the reply in the reply box and indicates to send thereply. The reply is received (e.g., by the share component 310 and theselling component 312) in operation 710. The reply is then transmittedin operation 712. In one embodiment, the reply is shared with thepublication system 120 via the share component 310 (via the networkcomponent 304). In alternative embodiments, the reply may be transmittedusing other methods. The publication system 120 (e.g., by way of themessaging engine 416) receives the reply and shares the reply with thepotential buyer.

FIG. 8 is a flow diagram of an example method 800 for managing post-saleof an item using the native selling platform provided by the OS 306. Inoperation 802, a sale of the item is detected. For example, thepublication system 120 facilitates the sale of the item by providing thelisting on the publication system 120 and managing a process to sell theitem (e.g., auction or fixed priced sale). The publication system 120(e.g., via the messaging engine 416) shares a notification that the itemhas sold with the share component 310 of the mobile device 200.

Accordingly, in operation 804, a sales notification is presented by theshare component 310 (via the selling component 312 and the userinterface component 306) on a home page of the mobile device 200 whilethe mobile device 200 is in a standby mode. In example embodiments, thesales notification is a push notification provided on the home pagewithout activation of any applications on the mobile device 200. Thesold notification indicates that the item that the user listed using thenative selling platform has sold.

In response to receiving the sale notification, the user performs anaction (e.g., swipe) on the sale notification to trigger interactionwith the sale notification. In example embodiments, the user does notneed to unlock or take the mobile device 200 off standby mode in orderto interact with the sale notification. The action causes presentationof various post-sale options in operation 806. For example, the user caninitiate a shipping process or a pick-up process through selection ofone of the post-sale options. Accordingly in operation 808, a selectionof one of the post-sale options is received by the share component 310.

A determination is made in operation 810 whether the selection is toinitiate the shipping (or delivery) process or to initiate the pick-upprocess. If the selection is to initiate the pick-up process, then inoperation 812, a user interface that allows the user to indicate alocation and time for pick-up of the item is presented. In exampleembodiments, the pick-up information is “shared” by the share component310 with the publication system 120 (e.g., with the messaging engine416). Subsequently, the publication system 120 (e.g., by way of themessaging engine 416) provides the pick-up information to the buyer.

Alternatively, if the selection is to initiate the shipping process, ashipping label may be displayed in operation 814. The user can thenprint the shipping label and prepare the item for shipping to the buyer.

FIG. 9 is a block diagram illustrating components of a machine 900,according to some example embodiments, able to read instructions 924from a machine-readable medium 922 (e.g., a non-transitorymachine-readable medium, a machine-readable storage medium, acomputer-readable storage medium, or any suitable combination thereof)and perform any one or more of the methodologies discussed herein, inwhole or in part. Specifically, FIG. 9 shows the machine 900 in theexample form of a computer system (e.g., a computer) within which theinstructions 924 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 900 to performany one or more of the methodologies discussed herein may be executed,in whole or in part.

In alternative embodiments, the machine 900 operates as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine 900 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 900 may be a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a set-top box (STB), a personal digital assistant(PDA), a cellular telephone, a smartphone, a web appliance, a networkrouter, a network switch, a network bridge, or any machine capable ofexecuting the instructions 924, sequentially or otherwise, that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 924 to perform any one or more of the methodologiesdiscussed herein.

The machine 900 includes a processor 902 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 904, and a static memory 906, which areconfigured to communicate with each other via a bus 908. The processor902 may contain microcircuits that are configurable, temporarily orpermanently, by some or all of the instructions 924 such that theprocessor 902 is configurable to perform any one or more of themethodologies described herein, in whole or in part. For example, a setof one or more microcircuits of the processor 902 may be configurable toexecute one or more modules (e.g., software modules) described herein.

The machine 900 may further include a graphics display 910 (e.g., aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, a cathode ray tube (CRT), orany other display capable of displaying graphics or video). The machine900 may also include an alphanumeric input device 912 (e.g., a keyboardor keypad), a cursor control device 914 (e.g., a mouse, a touchpad, atrackball, a joystick, a motion sensor, an eye tracking device, or otherpointing instrument), a storage unit 916, a signal generation device 918(e.g., a sound card, an amplifier, a speaker, a headphone jack, or anysuitable combination thereof), and a network interface device 920.

The storage unit 916 includes the machine-readable medium 922 (e.g., atangible and non-transitory machine-readable storage medium) on whichare stored the instructions 924 embodying any one or more of themethodologies or functions described herein. The instructions 924 mayalso reside, completely or at least partially, within the main memory904, within the processor 902 (e.g., within the processor's cachememory), or both, before or during execution thereof by the machine 900.Accordingly, the main memory 904 and the processor 902 may be consideredmachine-readable media (e.g., tangible and non-transitorymachine-readable media).

In some example embodiments, the machine 900 may be a portable computingdevice, such as a smart phone or tablet computer, and have one or moreadditional input components (e.g., sensors or gauges). Examples of suchinput components include an image input component (e.g., one or morecameras), an audio input component (e.g., a microphone), a directioninput component (e.g., a compass), a location input component (e.g., aglobal positioning system (GPS) receiver), an orientation component(e.g., a gyroscope), a motion detection component (e.g., one or moreaccelerometers), an altitude detection component (e.g., an altimeter),and a gas detection component (e.g., a gas sensor). Inputs harvested byany one or more of these input components may be accessible andavailable for use by any of the modules described herein.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 922 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions. The term “machine-readable medium” shall also be taken toinclude any medium, or combination of multiple media, that is capable ofstoring instructions for execution by a machine (e.g., machine 900),such that the instructions, when executed by one or more processors ofthe machine (e.g., processor 902), cause the machine to perform any oneor more of the methodologies described herein. Accordingly, a“machine-readable medium” refers to a single storage apparatus ordevice, as well as “cloud-based” storage systems or storage networksthat include multiple storage apparatus or devices. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, one or more data repositories in the form of asolid-state memory, an optical medium, a magnetic medium, or anysuitable combination thereof.

Furthermore, the tangible machine-readable medium is non-transitory inthat it does not embody a propagating signal. However, labeling thetangible machine-readable medium as “non-transitory” should not beconstrued to mean that the medium is incapable of movement—the mediumshould be considered as being transportable from one physical locationto another. Additionally, since the machine-readable medium is tangible,the medium may be considered to be a machine-readable device.

The instructions 924 may further be transmitted or received over acommunications network 926 using a transmission medium via the networkinterface device 920 and utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, plain old telephone service (POTS)networks, and wireless data networks (e.g., WiFi, LTE, and WiMAXnetworks). The term “transmission medium” shall be taken to include anyintangible medium that is capable of storing, encoding, or carryinginstructions for execution by the machine, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such software.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A “hardware module” is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as afield-programmable gate array (FPGA) or an ASIC. A hardware module mayalso include programmable logic or circuitry that is temporarilyconfigured by software to perform certain operations. For example, ahardware module may include software encompassed within ageneral-purpose processor or other programmable processor. It will beappreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software mayaccordingly configure a processor, for example, to constitute aparticular hardware module at one instance of time and to constitute adifferent hardware module at a different instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Some portions of the subject matter discussed herein may be presented interms of algorithms or symbolic representations of operations on datastored as bits or binary digital signals within a machine memory (e.g.,a computer memory). Such algorithms or symbolic representations areexamples of techniques used by those of ordinary skill in the dataprocessing arts to convey the substance of their work to others skilledin the art. As used herein, an “algorithm” is a self-consistent sequenceof operations or similar processing leading to a desired result. In thiscontext, algorithms and operations involve physical manipulation ofphysical quantities. Typically, but not necessarily, such quantities maytake the form of electrical, magnetic, or optical signals capable ofbeing stored, accessed, transferred, combined, compared, or otherwisemanipulated by a machine. It is convenient at times, principally forreasons of common usage, to refer to such signals using words such as“data,” “content,” “bits,” “values,” “elements,” “symbols,”“characters,” “terms,” “numbers,” “numerals,” or the like. These words,however, are merely convenient labels and are to be associated withappropriate physical quantities.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or any suitable combination thereof), registers, orother machine components that receive, store, transmit, or displayinformation. Furthermore, unless specifically stated otherwise, theterms “a” or “an” are herein used, as is common in patent documents, toinclude one or more than one instance. Finally, as used herein, theconjunction “or” refers to a non-exclusive “or,” unless specificallystated otherwise.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader spirit and scope of embodiments of the present invention. Suchembodiments of the inventive subject matter may be referred to herein,individually or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single invention or inventive concept if more thanone is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent invention. In general, structures and functionality presented asseparate resources in the example configurations may be implemented as acombined structure or resource. Similarly, structures and functionalitypresented as a single resource may be implemented as separate resources.These and other variations, modifications, additions, and improvementsfall within a scope of embodiments of the present invention asrepresented by the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense.

What is claimed is:
 1. A method comprising: receiving, by a publicationsystem, an image of an item and parameters used to generate a listingfor the item, the image and the parameters received responsive to anindication to list the item via a listing user interface that is nativeto a device operating system, the listing user interface presentedresponsive to selection of a service associated with the publicationsystem and via a sharing user interface that is native to the deviceoperating system; generating, by the publication system, the listing forthe item based on the image and the parameters; and surfacing, by thepublication system, the listing of the item via the selected service. 2.The method as described in claim 1, wherein the selected service is asocial network to which data corresponding to the listing is postable.3. The method as described in claim 2, wherein the surfacing includesposting the data corresponding to the listing with the social network.4. The method as described in claim 1, further comprising determininghashtags that correspond to the listing for presentation via the listinguser interface.
 5. The method as described in claim 4, furthercomprising: receiving a selection of at least one of the hashtags; andincluding the at least one hashtag in the listing.
 6. The method asdescribed in claim 1, further comprising: receiving at least one hashtagentered by user input via the listing user interface; and including theat least one hashtag in the listing.
 7. The method as described in claim1, further comprising: generating a publication-system notification; andcommunicating the publication-system notification to a computing devicefor presentation on a home page native to the device operating system.8. The method as described in claim 7, wherein the publication-systemnotification is a question about the listing of the item or a salenotification.
 9. A non-transitory machine-readable storage mediumcomprising instructions that, when executed by one or more processors ofa device, cause the device to implement a publication system byperforming operations comprising: receiving an image of an item andparameters used to generate a listing for the item, the image and theparameters received responsive to an indication to list the item via alisting user interface that is native to a device operating system, thelisting user interface presented responsive to selection of a serviceassociated with the publication system and via a sharing user interfacethat is native to the device operating system; generating the listingfor the item based on the image and the parameters; and surfacing thelisting of the item via the selected service.
 10. The non-transitorymachine-readable storage medium as described in claim 9, wherein theselected service is a social network to which data corresponding to thelisting is postable.
 11. The non-transitory machine-readable storagemedium as described in claim 10, wherein the surfacing includes postingthe data corresponding to the listing with the social network.
 12. Thenon-transitory machine-readable storage medium as described in claim 9,wherein the operations further comprise determining hashtags thatcorrespond to the listing for presentation via the listing userinterface.
 13. The non-transitory machine-readable storage medium asdescribed in claim 12, wherein the operations further comprise:receiving a selection of at least one of the hashtags; and including theat least one hashtag in the listing.
 14. The non-transitorymachine-readable storage medium as described in claim 9, wherein theoperations further comprise: receiving at least one hashtag entered byuser input via the listing user interface; and including the at leastone hashtag in the listing.
 15. The non-transitory machine-readablestorage medium as described in claim 9, wherein the operations furthercomprise: generating a publication-system notification; andcommunicating the publication-system notification to a computing devicefor presentation on a home page native to the device operating system.16. The non-transitory machine-readable storage medium as described inclaim 15, wherein the publication-system notification is a questionabout the listing of the item or a sale notification.
 17. A publicationsystem comprising: at least one processor; and a memory storinginstructions that, when executed by the at least one processor, causethe publication system to perform operations comprising: receiving animage of an item and parameters used to generate a listing for the item,the image and the parameters received responsive to an indication tolist the item via a listing user interface that is native to a deviceoperating system, the listing user interface presented responsive toselection of a service associated with the publication system and via asharing user interface that is native to the device operating system;generating the listing for the item based on the image and theparameters; and surfacing the listing of the item via the selectedservice.
 18. The publication system as described in claim 17, whereinthe selected service is a social network to which data corresponding tothe listing is postable.
 19. The publication system as described inclaim 18, wherein the surfacing includes posting the data correspondingto the listing with the social network.
 20. The publication system asdescribed in claim 17, wherein the operations further comprisedetermining hashtags that correspond to the listing for presentation viathe listing user interface.